Methods and apparatus for the utilization of core based nodes for state transfer

ABSTRACT

Methods and apparatus for storing, manipulating, retrieving, and forwarding state, e.g., context and other information, used to support communications sessions with one or more end nodes, e.g., mobile devices, are described. Various features are directed to a mobile node controlling the transfer of state from a first access node to a second access node during a handoff operation thereby eliminating any need for state transfer messages to be transmitted between the second access node and the first access node during handoff. Other features of the invention are directed to the use of a core network node to store state information. State information stored in the core node can be accessed and used by access nodes in cases where a mobile node does not send a state transfer message during a handoff, e.g., because communication with the first access node is lost or because such messages are not supported.

RELATED APPLICATIONS

The present application is a continuation of U.S. patent applicationSer. No. 11/247,395 filed Oct. 11, 2005 now U.S. Pat. No. 7,369,855,which is a continuation of U.S. patent application Ser. No. 10/910,447filed Aug. 3, 2004 now U.S. Pat. No. 6,990,337, which is a continuationof U.S. patent application Ser. No. 10/369,998 filed Feb. 18, 2003 nowU.S. Pat. No. 6,862,446 which claims the benefit of U.S. ProvisionalPatent Application Ser. No. 60/444,299 filed Jan. 31, 2003 which has thesame title as the present application and which is hereby expresslyincorporated by reference.

BACKGROUND OF INVENTION

Communications system frequently include a plurality of network nodeswhich are coupled to access nodes through which end nodes, e.g., mobiledevices, are coupled to the network. Network nodes may be arranged in ahierarchy. Access Authentication and Authorization (AAA) servers arenodes which are normally placed relatively high in the networkhierarchy. They normally provide information used for security andaccess control purposes. Access nodes frequently have a secure link withan AAA server in cases where such servers are used. The secure link maybe through one or more node in the hierarchy.

Operators typically manage access sessions in IP networks using theRADIUS protocol and associated RADIUS AAA servers. In the future, AAAsystems may be based on new protocols such as DIAMETER. In a systemusing a RADIUS AAA server, when a user attempts to gain access to anoperator network, for the duration of an access session, the localAccess Router normally issues one or more RADIUS Access-Requests to anAuthentication Server to authenticate that user based on its identitysuch as a Network Access Identifier (NAI). The AAA database typicallyhas stored the identities of those users allowed to access its systemalong with the services features they are able to invoke. When the useris successfully authenticated, its access port on the access device isconfigured with policy state commensurate with the user's serviceAuthorization. The service authorization is normally delivered viaRADIUS to the Access Router by the Authorization Server. Whilstauthorized, service usage during an access session is recorded by theAccess Router, and sent as accounting records to an Accounting Serverusing Accounting-Request messages in the RADIUS protocol. The AccountingServer may be part of the AAA server or it may be an independent serverusing the same protocol with the authorization server. If the user isconnected to multiple Access Routers during a single session then themultiple sessions need to be aggregated in the Accounting Servers.

In addition to authorization and accounting issues, communicationssystems which support mobile devices need to include mechanisms forconveying location information so that a mobile device can change itspoint of attachment to the network and still have signals, e.g., IPpackets, routed to it.

Mobile IP, (versions 4 and 6) also known as MIPv4 [MIPv4] and MIPv6[MIPv6], enables a mobile node (MN) to register its temporary locationindicated by a care-of-address (CoA) to its Home Agent (HA). The HA thenkeeps a mapping (also called a binding) between the MN's permanentaddress, otherwise called Home Address (HoA), and the registered CoA sothat packets for that MN can be redirected to its current location usingIP encapsulation techniques (tunneling). The CoA used by a MN can be anaddress that belongs to a Foreign Agent (FA) in an Access Router whenMIPv4 is used or it can be a temporarily allocated address to the MNitself, from the Access Router prefix, in which case it is called acollocated care-of-address (CCoA). The latter model also applies toMIPv4 while it is the only mode of operation in MIPv6. Note that for thepurpose of this document the terms CCoA and CoA as well as Registrationand Binding Update (BU) are interchangeable since they are thecorresponding terms for MIPv4 and MIPv6. The methods and apparatus ofthe invention are applicable to both MIPv4 and MIPv6 unless otherwisementioned.

AAA systems are typically used with mobile IP to manage IP addressallocations (HoAs), to dynamically allocate HAs, to distribute MNprofiles to the Access Router and also to distribute security keys toauthenticate MIP messages and to secure the air-link. The Mobile Node,an end node which is capable of changing its point of networkattachment, typically sends a MIP message to gain access to the system,which triggers a AAA request to authenticate and authorize the MobileNode. The AAA MN profile and security state is then passed from the AAAsystem to the Access Router to control services consumed by the MN.

MNs may change their point of network attachment, e.g., as they movefrom one cell to another cell. This involves changing the MNs point ofattachment from a first access node, e.g., a first router, to a secondaccess node, e.g., a second router. This processes is commonly known asa handoff As part of a handoff the MN's CoA/CCoA needs to be updated andthen transferred into the HA using MIP signaling so that packets areredirected to the MN via the new Access Router. As part of handoffprocess, it is necessary to transfer at least some of the first accessrouter's state information corresponding to the MN involved in thehandoff to the new access router so that the MN service is notinterrupted. This process is known as State Transfer. State transfer mayinclude, e.g., the transfer of AAA profile state information that waspreviously delivered via RADIUS to the AR, at which the MN accesssession commenced. It also may include, e.g., the transfer of air-linksecurity vectors, MN-NAI, MN IP Address, MN-EUI-64, remaining MIPRegistration Lifetime, MN multicast group membership, admission controlstate, resource reservation state, diff-serv state, SIP session state,compressor state, MN scheduling history and/or many other potentialitems of MN specific AR state information.

In at least one known system, the transfer of state information during ahandoff is accomplished by the new access node to which a mobile node isconnecting sending a state transfer message through the communicationsnetwork to the old access node to which the mobile node was connected.In response the old access node forwards state information to the newaccess node. This technique, while effective, has the disadvantage ofrequiring that a message be sent between the old and new access nodes toinitiate the transfer of the state information. The links between accessnodes used for the transmission of such messages may become congested orcould be used to convey other information and/or signals if the need formessages between access nodes used to initiate the transfer of stateinformation could be eliminated.

In view of the above discussion, it should be appreciated that there isa need for new methods of implementing the communication of stateinformation to a new access node in the case of a mobile node handoff orin other cases where a mobile node enters a new cell. It should also beappreciated that, for the reasons discussed above, avoiding the use ofmessages between access nodes to trigger the transfer of stateinformation during a handoff is desirable.

SUMMARY OF THE INVENTION

In a wireless network, mobile end users use end nodes, e.g., wirelessdevices, to communicate with other network entities, e.g., wirelessdevices used by other end users, via access nodes. The access nodes maybe implemented as wireless access routers. Associated with each end nodethere is state, e.g., a set of information comprising various parametersrelating to service(s) and/or application(s) corresponding to the endnode. This state is used by an access router which serves as the endnode's point of network attachment. Each time the end node changes thepoint of attachment to the network, the state needs to be re-built ortransferred to the access router which serves as the new point ofnetwork attachment so that the new access node can continue to providecommunication services with regard to existing communications sessionsor provide new communications services, e.g., as requested by the endnode. This document describes the concept of state transfer betweenaccess points/routers as well as a novel way to gather the requiredstate and transfer it from one point to the next.

This application describes methods for transfer of state to supportevents such as the movement of an end node (EN) between access nodes(ANs). The method uses Core State Management Nodes (CSMNs) located inthe core of the network, to store, process and forward state informationfor the end nodes. The CSMNs used to store and transfer stateinformation in accordance with the invention may be implemented as partof Authentication Authorization & Accounting (AAA) server similar to thetype found in many systems.

In accordance with one feature of the invention, access nodes can storestate information in a CSMN and can also retrieve, e.g., fetch, statecorresponding to an end node from the CSMN used to store thatinformation. Access nodes normally update the stored state for an endnode for which they serve as the network point of attachment when theend node signals an intent to end communication with the access node orcommunication ceases, e.g., because communication with the access nodeis interrupted or terminated prior to completion of a handoff operation.

An access node normally retrieves state information from the CSMN whencommunication with an end node is initiated, e.g., when the end nodeenters the cell corresponding to the access node. However, in the caseof a handoff, in some embodiments, state information is forwarded fromthe access node which was previously servicing the end node eliminatingthe need to retrieve state information from the CSMN.

In accordance with one feature of the invention, during handoff, themobile node controls the forwarding of state from the first to thesecond access node being used by the end node. This is accomplished bythe end node sending a message to the first access node to forward stateinformation to the second access node. This approach avoids the need forthe second node to send a message to the first node requesting thetransfer of state information thereby reducing the amount of signalingbetween access nodes as compared to system which employ such statetransfer messages between access nodes.

In cases where communication is lost with the first access node beforethe end node can transmit the state transfer signal, the second accessnode will retrieve the state information from the CSMN. Use of thetransfer message is optional but has the advantage of reducing thenumber of information retrieval operations which need to be supported bythe core node. In addition, the use of the transfer message directedfrom the end node to the first access node has the advantage of reducingdelays in terms of the amount of time between when the end node beginscommunication with the second access node and when the second accessnode obtains the state information to be used in servicing the end node.The state transfer message may trigger updating of the state informationin the core node in addition to the transfer of state information to thesecond access node.

State information stored by an access node in the CSMN and/ortransferred to another access node will normally reflect any localchanges to that state, e.g., changes made at the access node which isstoring or transferring the state subsequent to the state informationbeing received either from the CSMN or another access node. Stored statemay also be manipulated and modified by the CSMN itself, e.g., as systemor session requirements change during an end node access session orother communication operation.

Additional features and benefits of the present invention are discussedin the detailed description which follows.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a network diagram of an exemplary communicationssystem in which the invention is applicable.

FIG. 2 illustrates an exemplary end node implemented in accordance withthe present invention.

FIG. 3 illustrates an exemplary access node implemented in accordancewith the present invention.

FIG. 4 illustrates an exemplary Core State Management Node implementedin accordance with the present invention.

FIG. 5 illustrates signaling performed in accordance with the presentinvention when an end node transitions from one access node to anotheraccess node.

FIG. 6 illustrates signaling performed in accordance with the presentinvention when an end node transitions from one access node to anotheraccess node when the access nodes use different CSMN nodes.

FIG. 7 illustrates alternative signaling performed from FIG. 6.

FIG. 8 illustrates alternative signaling performed from FIGS. 6 & 7 whenCSMNs are arranged in a hierarchy.

FIG. 9 illustrates a mechanism for CSMN polling of aggregated state fromaccess nodes

FIG. 10 illustrates an embodiment of this invention based on the AAAsystem

DETAILED DESCRIPTION

The methods and apparatus of the present invention for storing,manipulating, retrieving, and forwarding state, e.g., context and otherinformation, used to support communications sessions with one or moreend nodes, e.g., mobile devices, can be used with a wide range ofcommunications systems. For example the invention can be used withsystems which support mobile communications devices such as notebookcomputers equipped with modems, PDAs, and a wide variety of otherdevices which support wireless interfaces in the interests of devicemobility.

FIG. 1 illustrates an exemplary communication system 100, e.g., acellular communication network, which comprises a plurality of nodesinterconnected by communications links. Nodes in the exemplarycommunication system 100 exchange information using signals, e.g.,messages, based on communication protocols, e.g., the Internet Protocol(IP). The communications links of the system 100 may be implemented, forexample, using wires, fiber optic cables, and/or wireless communicationstechniques. The exemplary communication system 100 includes a pluralityof end nodes 144, 146, 144′, 146′, 144″, 146″, which access thecommunication system via a plurality of access nodes 140, 140′, 140″.The end nodes 144, 146, 144′, 146′, 144″, 146″ may be, e.g., wirelesscommunication devices or terminals, and the access nodes 140, 140′, 140″may be, e.g., wireless access routers or base stations. The exemplarycommunication system 100 also includes a number of other nodes 104, 106,110, and 112, used to provide interconnectivity or to provide specificservices or functions. Specifically, the exemplary communication system100 includes a Core State Management node (CSMN) 104, used to supporttransfer and storage of state pertaining to end nodes. The CSMN node maybe part of an AAA server.

The FIG. 1 exemplary system 100 depicts a network 102 that includes theCSMN 104 and the node 106, both of which are connected to anintermediate network node 110 by a corresponding network link 105 and107, respectively. The intermediate network node 110 in the network 102also provides interconnectivity to network nodes that are external fromthe perspective of the network 102 via network link 111. Network link111 is connected to another intermediate network node 112, whichprovides further connectivity to a plurality of access nodes 140, 140′,140″ via network links 141, 141′, 141″, respectively.

Each access node 140, 140′, 140″ is depicted as providing connectivityto a plurality of N end nodes (144, 146), (144′, 146′), (144″, 146″),respectively, via corresponding access links (145, 147), (145′, 147′),(145″, 147″), respectively. In the exemplary communication system 100,each access node 140, 140′, 140″ is depicted as using wirelesstechnology, e.g., wireless access links, to provide access. A radiocoverage area, e.g., communications cell, 148, 148′, 148″ of each accessnode 140, 140′, 140″, respectively, is illustrated as a circlesurrounding the corresponding access node.

The exemplary communication system 100 is subsequently used as a basisfor the description of various embodiments of the invention. Alternativeembodiments of the invention include various network topologies, wherethe number and type of network nodes, the number and type of accessnodes, the number and type of end nodes, the number and type of CSMNs,the number and type of links, and the interconnectivity between nodesmay differ from that of the exemplary communication system 100 depictedin FIG. 1.

In various embodiments of the present invention some of the functionalentities depicted in FIG. 1 may be omitted or combined. The location orplacement of these functional entities in the network may also bevaried.

FIG. 2 provides a detailed illustration of an exemplary end node 200implemented in accordance with the present invention. The exemplary endnode 200, depicted in FIG. 2, is a detailed representation of anapparatus that may be used as any one of the end nodes 144, 146, 144′,146′, 144″, 146″, depicted in FIG. 1. In the FIG. 2 embodiment, the endnode 200 includes a processor 204, a wireless communication interface230, a user input/output interface 240 and memory 210 coupled togetherby bus 206. Accordingly, via bus 206 the various components of the endnode 200 can exchange information, signals and data. The components 204,206, 210, 230, 240 of the end node 200 are located inside a housing 202.

The wireless communication interface 230 provides a mechanism by whichthe internal components of the end node 200 can send and receive signalsto/from external devices and network nodes, e.g., access nodes. Thewireless communication interface 230 includes, e.g., a receiver circuit232 with a corresponding receiving antenna 236 and a transmitter circuit234 with a corresponding transmitting antenna 238 used for coupling theend node 200 to other network nodes, e.g., via wireless communicationschannels.

The exemplary end node 200 also includes a user input device 242, e.g.,keypad, and a user output device 244, e.g., display, which are coupledto bus 206 via the user input/output interface 240. Thus, userinput/output devices 242, 244 can exchange information, signals and datawith other components of the end node 200 via user input/outputinterface 240 and bus 206. The user input/output interface 240 andassociated devices 242, 244 provide a mechanism by which a user canoperate the end node 200 to accomplish various tasks. In particular, theuser input device 242 and user output device 244 provide thefunctionality that allows a user to control the end node 200 andapplications, e.g., modules, programs, routines and/or functions, thatexecute in the memory 210 of the end node 200.

The processor 204 under control of various modules, e.g., routines,included in memory 210 controls operation of the end node 200 to performvarious signaling and processing as discussed below. The modulesincluded in memory 210 are executed on startup or as called by othermodules. Modules may exchange data, information, and signals whenexecuted. Modules may also share data and information when executed. Inthe FIG. 2 embodiment, the memory 210 of end node 200 of the presentinvention includes a signaling/control module 212 and signaling/controldata 214.

The signaling/control module 212 controls processing relating toreceiving and sending signals, e.g., messages, for management of stateinformation storage, retrieval, and processing. Signaling/control data214 includes state information, e.g., parameters, status and/or otherinformation relating to operation of the end node. In particular, thesignaling/control data 214 may include configuration information 216,e.g., end node identification information, and operational information218, e.g., information about current processing state, status of pendingresponses, etc. The module 212 may access and/or modify the data 214,e.g., update the configuration information 216 and/or the operationalinformation 218.

FIG. 3 provides a detailed illustration of an exemplary access node 300implemented in accordance with the present invention. The exemplaryaccess node 300, depicted in FIG. 3, is a detailed representation of anapparatus that may be used as any one of the access nodes 140, 140′,140″ depicted in FIG. 1. In the FIG. 3 embodiment, the access node 300includes a processor 304, memory 310, a network/internetwork interface320 and a wireless communication interface 330, coupled together by bus306. Accordingly, via bus 306 the various components of the access node300 can exchange information, signals and data. The components 304, 306,310, 320, 330 of the access node 300 are located inside a housing 302.

The network/internetwork interface 320 provides a mechanism by which theinternal components of the access node 300 can send and receive signalsto/from external devices and network nodes. The network/internetworkinterface 320 includes, a receiver circuit 322 and a transmitter circuit324 used for coupling the node 300 to other network nodes, e.g., viacopper wires or fiber optic lines. The wireless communication interface330 also provides a mechanism by which the internal components of theaccess node 300 can send and receive signals to/from external devicesand network nodes, e.g., end nodes. The wireless communication interface330 includes, e.g., a receiver circuit 332 with a correspondingreceiving antenna 336 and a transmitter circuit 334 with a correspondingtransmitting antenna 338. The interface 330 is used for coupling theaccess node 300 to other network nodes, e.g., via wireless communicationchannels.

The processor 304 under control of various modules, e.g., routines,included in memory 310 controls operation of the access node 300 toperform various signaling and processing. The modules included in memory310 is executed on startup or as called by other modules that may bepresent in memory 310. Modules may exchange data, information, andsignals when executed. Modules may also share data and information whenexecuted. In the FIG. 3 embodiment, the memory 310 of the access node300 of the present invention includes a State Management module 312 anda Signaling/Control module 314. Corresponding to each of these modules,memory 310 also includes State Management data 313 and theSignaling/Control data 315.

The State Management Module 312 controls the processing of receivedsignals from end nodes or other network nodes regarding state storageand retrieval. The State Management Data 313 includes, e.g., end-noderelated information such as the state or part of the state, or thelocation of the current end node state if stored in some other networknode. The State Management module 312 may access and/or modify the StateManagement data 313.

The Signaling/Control module 314 controls the processing of signalsto/from end nodes over the wireless communication interface 330, andto/from other network nodes over the network/internetwork interface 320,as necessary for other operations such as basic wireless function,network management, etc. The Signaling/Control data 315 includes, e.g.,end-node related data regarding wireless channel assignment for basicoperation, and other network-related data such as the address ofsupport/management servers, configuration information for basic networkcommunications. The Signaling/Control module 314 may access and/ormodify the Signaling/Control data 315.

FIG. 4 provides a detailed illustration of an exemplary Core StateManagement Node 400 implemented in accordance with the presentinvention. The exemplary CSMN 400, depicted in FIG. 4, is a detailedrepresentation of an apparatus that may be used as the CSMN 104 depictedin FIG. 1. In the FIG. 4 embodiment, the CSMN 400 includes a processor404, memory 410, a network/internetwork interface 420, coupled togetherby bus 406. Accordingly, via bus 406 the various components of theaccess node 400 can exchange information, signals and data. Thecomponents 404, 406, 410, 420 of the access node 400 are located insidea housing 402.

The network/internetwork interface 420 provides a mechanism by which theinternal components of the CSMN 400 can send and receive signals to/fromexternal devices and network nodes. The network/internetwork interface420 includes, a receiver circuit 422 and a transmitter circuit 424 usedfor coupling the node 400 to other network nodes, e.g., via copper wiresor fiber optic lines.

The processor 404 under control of various modules, e.g., routines,included in memory 410 controls operation of the CSMN 400 to performvarious signaling and processing. The module included in memory 410 isexecuted on startup or as called by other modules that may be present inmemory 410. In the FIG. 4 embodiment, the memory 410 of the CSMN 400 ofthe present invention includes a Core State Management module 412 and aCore State Management data 413.

The Core State Management Module 412 controls the processing of receivedsignals from other CSMN, access nodes, or network nodes regarding statestorage and retrieval. The Core State Management Data 413 includes,e.g., end-node state information. The Core State Management module 412may access and/or modify the Core State Management data 413.

FIGS. 5, 6, 7 and 8 illustrate the signaling performed in accordancewith an exemplary embodiment of the invention. The signaling isillustrated in the context of exemplary system 500, adapted from system100 illustrated in FIG. 1. Each of the access nodes 140, 140′ shown inFIGS. 5, 6, 7 and 8 are simplified representations of the exemplaryaccess node 300 depicted in FIG. 3. Additionally, in the exemplarysystem 500 the end nodes 144, 146, 144′, 146′, 144″, 146″ (andcorresponding access links 145, 147, 145′, 147′, 145″, 147″) from system100 have been replaced for purposes of explaining the invention with asingle end node, X 146, implemented in accordance with the invention.End node, X, 146 shown in FIGS. 5, 6, 7 and 8 is a simplifiedrepresentation of end node 200 depicted in FIG. 2 and is coupled to thedepicted access nodes by one or more wireless communications links.

End node state information transferred between access nodes and corestate management nodes in accordance with the present invention is stateinformation relating to, e.g., used to support, communication with theend node which operates as part of the system. In one embodiment of thisinvention transferred state information will typically include static,long lived and short lived components. Static components may includeparameters that do not change over long periods of time and multiplecommunication sessions. Examples of static state are end node profileinformation such as general quality of service parameters (e.g.: peakrates allowed) and generic authorization state (e.g.: type of data callsallowed). Examples of long lived state are parameters that do not changeduring the duration of a communication session (e.g.: a dynamicallyassigned Internet address or some long lived security information).Examples of short lived state are parameters that are very dynamic innature and change multiple times during a communications session (e.g.:dynamic quality of service state, multicast group membership, etc.)

In one embodiment of this invention state information (static, short andlong lived) is moved together according to methods described in thepresent invention. In an alternative embodiment static state residespermanently in CSMNs. In this case both static and dynamic state may betransferred between CSMNs located in different regions, or from CSMN toaccess nodes. However, while dynamic state information is normallytransferred from access nodes to CSMNs, there is no need to communicatestatic state information to the CSMNs since they already include theinformation. In an alternative embodiment, all state resides in one ormore CSMNs and access nodes and/or CSMNs may update said state as statechanges occur.

CSMN Operation

CSMN operation in accordance with one feature of the invention will nowbe described with reference to FIG. 5. FIG. 5 illustrates core statemanagement signaling in a simplified version of the exemplary systemdepicted in the FIG. 1 and described above. The depicted signaling mayoccur as part of a handoff operation. FIG. 5 includes access nodes 140,140′ implemented according to FIG. 3, end node X 146 implementedaccording to FIG. 2 and a Core State Management Node (CSMN) 104implemented according to FIG. 4. Lines between the nodes of FIG. 5represent state management related messages sent and received accordingto the present invention and are explained below. Dashed lines betweennodes of FIG. 5 indicate optional messages.

In FIG. 5 End Node X 146 sends, e.g., at the start of a handoff, a StoreState Request (SSRQ) message 510 to Access Node 140 comprising the EndNode X 146 identifier. An end node identifier may be a network address,hardware address, or other identification specific to the user or thedevice associated with the end node. On reception of the SSRQ message510 the Access Node 140 searches its State Management data 313 (FIG. 3)for state information associated with said end node and sends a AccessNode State Transfer Update (AN-STU) message 520 to the Core StateManagement Node (CSMN) 104. Said AN-STU message 520 comprises the EndNode X 146 identifier and state associated with said end node asavailable to Access Node 140.

On reception of the AN-STU message 520 the Core State Management Module412 (FIG. 4) of CSMN Node 104 processes the message and stores the stateincluded in said message in its CSM data 413 (FIG. 4) such that saidstate is associated with the identifier of the end node also included insaid message. CSMN node 104 optionally returns a State transfer UpdateAcknowledgement (STUAck) message 530 to Access Node 140 indicating thecorrect reception and storage of said state. Access Node 140 onreception of STUAck message 530 optionally sends a Store State Reply(SSRP) message 540 to End Node X 146 indicating the successful storageof said state in the core.

End Node X 146 sends a Retrieve State Request (RSRQ) message 550 toAccess Node 140′ comprising the End Node X 146 identifier. On receptionof said RSRQ message 550 Access Node 140′ sends a State Transfer Request(STRQ) message 560 comprising the identifier of End Node X 146 to CSMNnode 104. On reception of said STRQ message 560, the Core StateManagement module 412 (FIG. 4) of CSMN node 104 processes said messageand searches its core state management data 413 for state associatedwith the End Node X 146 indicated in said STRQ message. State associatedwith End Node X 146 that was earlier stored is found and a CSMN StateTransfer Update (CSMN-STU) message 570 including said state and theidentifier of End Node X 146 is sent to Access Node 140′. On receptionof CSMN-STU message 570, Access Node 140′ stores state included in saidmessage in its state management data 313 (FIG. 3). Access Node 140′optionally sends a Retrieve State Reply (RSRP) message 580 to End Node X146 to indicate the correct retrieval of state associated with said endnode from the core.

In an alternative embodiment of this invention the SSRQ message 510additionally includes the identifier of Access Node 140′ that End Node X146 wishes to exchange data with. In that case Access Node 140 sends anadditional copy of the AN-STU message 520 to the Access Node 140′ asindicated by AN-STU message 521. Access Node 140′ receives said messageand stores state included in said message and associated with said endnode. In this embodiment of the invention when Access Node 140′ receivesRSRQ message 550 it first checks its state management data 313 (FIG. 3)for state associated with said end node and only sends STRQ message 560if no state is found. In the same embodiment Access Node 140′ mayoptionally send a STUAck message 531 to Access Node 140 on reception ofthe AN-STU message 521.

In the various embodiments described above in regard to FIG. 5, aftersate information is transferred to the second access node 140′, networkrouting information corresponding to end node X 146 is updated so thatIP packets and other signals intended for end node X 146 will bedirected to the second access node 140′ instead of the first access node140. This is accomplished by one of the first and second access nodes140, 140′ sending a routing message to one or more network routingdevices. In the FIG. 5 example, node 120 is used to represent a routingdevice, e.g., a router, while messages 590 and 590′ represent routingupdate messages transmitted by the first and second access nodes 140,140′ respectively. Normally, only one of the access nodes will beresponsible for transmitting the routing update message. In mostembodiments this will be the second access node 140′ which transmits themessage 590′ once the state corresponding to end node X 146 has beensuccessfully received.

Removal of State from CSMN

State may be removed from the CSMN, e.g., upon expiration of a timer. Inone embodiment of this invention, on reception of AN-STU message 520,the CSMN 104, in addition to the processing described in the previoustwo sections, starts a timer of predetermined or negotiated value andassociates said timer with the state included in the received message520 and stored in its core state management data 413 (FIG. 4). When saidtimer expires, state associated with that timer and corresponding to anend node is removed from the core state management data 413 (FIG. 4) ofCSMN node 104. Removal of end node state upon timer expiration does notdepend on whether or not this state was requested through a STRQ messagewhile the timer was valid. Furthermore, if while the timer is stillvalid, the CSMN receives another AN-STU message, from the same ordifferent access node, comprising state for the same End Node X, thenthe CSMN re-sets the timer to its original value. Resetting the timer isdone whether or not the updated state is actually the same or differsfrom the existing stored state.

State Unavailable

In some cases, requested state information may not be available in theCSMN. In one embodiment of this invention, if no state is available forthe end node indicated in a received STRQ message 560, the CSMN 104returns a CSMN-STU message 570 including an indication that no state isavailable for said end node. In an alternative embodiment of thisinvention if no state is available for the end node indicated in areceived STRQ message 560, the CSMN 104 starts a predetermined ornegotiated timer and associates it with said message 560. If state forthe end node identified in message 560 is received, say in a AN-STUmessage 520, prior to the timer expiring, the CSMN processes message 520as described earlier and immediately stops the timer and sends aCSMN-STU message 570 to Access Node 140′. If the timer expires and noappropriate state is received then the CSMN node 104 returns a CSMN-STUmessage 570 including an indication that no state is available for saidend node. In a third embodiment of this invention if no state isavailable for the end node indicated in a received STRQ message 560, theCSMN 104 sends an optional Transfer State Request (TSRQ) message 561,comprising the identifier of End Node X 146 and the identifier of AccessNode 140′ that is currently requesting state, to the last access nodethat requested state for said end node X 146, i.e.: Access Node 140. Inthis case Access Node 140 sends the AN-STU message 521 to the AccessNode 140′ as indicated in FIG. 5. On reception of AN-STU message 521,Access Node 140′ stores state included in said message in its statemanagement data 313 (FIG. 3) and optionally returns acknowledgmentmessage 531 to Access Node 140.

State Updates

In one embodiment of this invention state information included in anAN-STU message 520, received by CSMN node 104 overwrites any existingstate information in the core state management data 413 (FIG. 4) of CSMN104. In an alternative embodiment of this invention multiple versions ofstate associated with a single end node are maintained in the CSMN 104,and only removed on expiration of associated timers or other triggerssuch as explicit messages from other network nodes.

State Manipulation at CSMN

In one embodiment of this invention the CSMN modifies state associatedwith an end node according to local policy before it sends it to arequesting access node in a CSMN-STU message 570.

State Indication from AN to EN

In one embodiment of this invention the RSRP message 580 from accessnode 140′ includes an indication of the state received by the accessnode in a corresponding CSMN-STU message 570. In one embodiment of thisinvention the indication provided is a digest which allows the end nodeto compare the received digest with a digest of the state it had at theaccess node 140, and to recognize whether the state is correct or not.In cases where the end node knows that the state should match or shoulddiffer from the one stored through access node 140, the end node cantake further action according to fault detection policies.

Loss of Link

In one embodiment of the present invention, Access Node 140 sends theAN-STU message 520 as soon as it detects the loss of connectivity withEnd Node X 146.

Core State Management between Regions: Reactive Approach

FIG. 6 depicts an alternative embodiment of the invention in whichAccess Nodes 140 and 140′ belong to different regions and thus store andretrieve state from different CSMN Nodes 104 and 104′ respectively. Inthis invention the term “region” is used to identify a multitude ofaccess nodes using the same CSMN node to store and retrieve statefrom/to. The breakdown of a large network into CSMN regions facilitatesthe scaling of state transfer methods described in this invention.

In FIG. 6 the processing and content of messages 510, 520, 530, 540 isidentical to that in FIG. 5 and thus are not described again here.Messages 650, 660, 670 and 680 are variations to corresponding messages550, 560, 570 and 580 in FIG. 5 and thus are described below togetherwith new messages 662, 663.

State associated with End Node X 146 is stored in CSMN node 104 with themethod described in FIG. 5 and messages 510, 520, 530 and 540. Followingthat, in this embodiment of the present invention End Node X 146 sendsRetrieve State Request (RSRQ) message 650 to Access Node 140′ includingthe End Node X 146 identifier and Region ID of the region of whichAccess Node 140 is a member. On reception of said RSRQ message 650Access Node 140′ sends State Transfer Request (STRQ) message 660including the identifier of End Node X 146 and the Access Node 140Region ID to CSMN node 104′. On reception of said STRQ message 660, thecore state management module 412 (FIG. 4) of CSMN node 104′ processessaid message and searches its core state management data 413 for stateassociated with the End Node X 146 indicated in said message. Stateassociated with End Node X 146 is not found and thus the CSMN node 104′sends Core State Transfer Request (Core-STRQ) message 663, comprisingthe identifier of End Node X 146, to CSMN node 104, which is the CSMNnode for the Region ID indicated in message 660.

On reception of said Core-STRQ message 663, the Core State Managementmodule 412 (FIG. 4) of CSMN node 104 processes said message and searchesits Core State Management data 413 for state associated with the EndNode X 146 indicated in said message. State associated with End Node X146 that was earlier stored is found and a Core State Transfer Update(Core-STU) message 662 including said state and the identifier of EndNode X 146 is sent to CSMN Node 104′. On reception of Core-STU message662, CSMN Node 104′ stores state included in said message in its CoreState Management data 413 (FIG. 4) and sends CSMN-STU message 670,including state associated with End Node X 146, to the requesting AccessNode 140′. On reception of CSMN-STU message 670, Access Node 140′ storesstate included in said message in its state management data 313 (FIG.3). Access Node 140′ optionally sends Retrieve State Reply (RSRP)message 680 to indicate the correct retrieval of state associated withsaid end node from the core.

Region ID to CSMN Mapping

In one embodiment of this invention the Region ID referred to aboveidentifies the CSMN node of the same region. In an alternativeembodiment of this invention the Region ID is of a structure that allowsthe resolution of that ID to an ID that identifies the CSMN Node of thatRegion.

Core State Management Between Regions: Proactive

FIG. 7 depicts an alternative method from that described in FIG. 6. InFIG. 7 End Node X 146 sends Store State Request (SSRQ) message 710 toAccess Node 140 including the End Node X 146 identifier and the RegionID corresponding to Access Node 140′. On reception of SSRQ message 710the Access Node 140 searches its state management data 313 (FIG. 3) forstate associated with said end node and sends a Access Node StateTransfer Update (AN-STU) message 720 to the Core State Management Node(CSMN) 104. Said AN-STU message 720 includes the End Node X 146identifier, the state associated with said end node as available toAccess Node 140, and the Region ID that was included in SSRQ message710.

On reception of AN-STU message 720, the core state management module 412(FIG. 4) of CSMN Node 104 processes the message, stores the stateincluded in said message in its core state management data 413 (FIG. 4)such that said state is associated with the identifier of the end nodealso included in said AN-STU message 720. CSMN Node 104 also observesthe Region ID in message 720 and thus sends a Core-STU message 763 toCSMN node 104′ which is the CSMN of the region associated with saidRegion ID. CSMN node 104′ optionally returns Core State Transfer UpdateAcknowledgement (Core-STUAck) message 762 to CSMN Node 104 indicatingthe correct reception and storage of said state. CSMN node 104 alsooptionally returns State transfer Update Acknowledgement (STUAck)message 730 to Access Node 140 indicating the correct reception andstorage of said state. Access Node 140 on reception of STUAck message730 optionally sends a Store State Reply (SSRP) message 740 to End NodeX 146 indicating the successful storage of said state in the core.

Messages 650, 660, 670 and 680 are now generated, processed andexchanged in the same way as described in FIG. 6, the difference beingthat CSMN node 104′ has state associated with End Node X 146 in its corestate management data 413 (FIG. 4) when it receives STRQ message 660from Access Node 140′. For that reason the CSMN-STU message 670 isimmediately returned.

Hierarchical Core State Management

FIG. 8 depicts an alternative embodiment of this invention in which CSMNNodes are arranged in a hierarchy so that high level CSMN Node 104″maintains copies of all or a part of the state maintained by low levelCSMN nodes 104 and 104′. In FIG. 8 messages 510, 520, 530, 540, 550,560, 570 and 580 are identical to those described in FIG. 5. Thedifference is that when the CSMN 104 receives message 520, in additionto the processing described in FIG. 5, the CSMN also sends a StateTransition Update (STU′) message 522 to CSMN Node 104″.

On reception of said STU′ message 522 including said state and theidentifier of End Node X 146, CSMN Node 104″ stores the state includedin said message in its Core State Management data 413 (FIG. 4) andoptionally returns a STUAck′ message 524 to CSMN Node 104 to indicatecorrect reception and storage of state. In addition, on reception ofSTRQ message 560, the core state management module 412 (FIG. 4) of CSMNnode 104′ processes said message and searches its core state managementdata 413 for state associated with the End Node X 146 indicated in saidmessage. State associated with End Node X 146 is not found and thus theCSMN node 104′ sends State Transfer Request (STRQ″) message 566,including the identifier of End Node X 146 to CSMN node 104″. Onreception of said STRQ″ message 566, the Core State Management module412 (FIG. 4) of CSMN node 104″ processes said message and searches itscore state management data 413 for state associated with the End Node X146 indicated in said message. State associated with End Node X 146 thatwas earlier stored is found and a State Transfer Update (STU″) message568 including said state and the identifier of End Node X 146 is sent toCSMN Node 104′. Now message 570 and the rest of the process described inFIG. 5 is completed as before.

State transfer in accordance with this invention may take place for anumber of reasons. In one embodiment of this invention state transfer isinitiated by an end node during a handoff process. The end node attemptsto terminate connection with one access node and establish a newconnection with another access node due to movement, in which case statetransfer as part of a mobility management system, enables the efficientand speedy establishment of connectivity with the new access node withas little interruption as possible to the end node data communication.In one embodiment of this invention the state transfer method describedis followed by a routing update message from the new access node or theend node redirecting any data traffic towards the new location of theend node. In one exemplary embodiment of this invention such a routingupdate would be in the form of Mobile IP registration, while in anotherembodiment would be a Mobile IPv6 binding update.

In an additional embodiment of this invention state transfer isinitiated as part of the transition of an end node from an active stateto a dormant state, where data communication is temporarily suspended.In this case state transfer ensures that when end node becomes activeagain at some future time and possibly at some different access node,connectivity can be initiated quickly and efficiently.

In a yet another embodiment of this invention state transfer isinitiated when a link between an end node and an access node is lost, inwhich case the state transfer mechanism is used for robustness, sincethe end node may attempt to reconnect via another access node at afuture time, again making the reconnection process quick and efficient.

FIG. 9 illustrates a communications system 800. FIG. 9 illustrates corestate management signaling in a simplified version of the exemplarysystem depicted in the FIG. 5. FIG. 5 includes access nodes 140, 140′that is the same as, or similar to, the access nodes described in regardto FIG. 3. End node X 146 is the same as, or similar to, end node X 146of FIG. 2. In addition, Core State Management Node (CSMN) 104 is thesame as, or similar to, the CSMN of FIG. 4. Lines between the nodes ofFIG. 9 represent state management related messages sent and receivedaccording to the present invention and are explained below.

In the FIG. 9 embodiment of the invention CSMN Node 104 periodically, orin response to some trigger event, sends Aggregated State Request (ASR)messages 801, 803 to access nodes 140, 140′ respectively. These requestmessages 801, 803 represent a request for state information. Onreception of said messages 801, 803, Access Nodes 140, 140′ aggregatethe current state information for end nodes associated with said AccessNode and return it to the CSMN Node 104 via messages 802, 804respectively. On reception of messages 802, 804 CSMN 104 de-aggregatesthe state and stores it in its memory per end node identifier. In thismanner the CSMN 104 can control updating of its state information. Thisupdate technique can be used in combination with the previouslydiscussed state update techniques. In on embodiment of this inventionnot all state is returned to the CSMN 104 but only the dynamic statethat periodically changes.

In one embodiment of the invention Aggregated State Request (ASR)messages 801, 803 are sent one at a time in a round robin way but alsoperiodically where the periodicity is preconfigured. In an alternativeembodiment of this invention Aggregated State Request (ASR) messages801, 803 are sent in a round robin way but at times were the loading onthe server is below a preconfigured threshold. Alternatively, othertechniques for scheduling and/or timing messages 801, 803 may be used.

In one embodiment of this invention state transfer is implementedoverlayed on the AAA system, in which case state transfer messages arenovel extensions to already existing AAA messages (e.g.: RADIUSmessages) or they are novel AAA messages. In such an embodiment, theCSMN node may be implemented as a AAA server and belongs to a AAAhierarchy. In an alternative embodiment of this invention the CSMN nodeis a Mobile Home Agent in which case state transfer messages areimplemented as novel extensions to already existing Mobile IP messagesor as novel Mobile IP messages. In one embodiment of this presentinvention, the system is a cellular network. In such an embodiment theaccess nodes maybe implemented as access routers. Network nodes may beimplemented as routers and end nodes may correspond to, e.g., beimplemented as, mobile nodes.

FIG. 10 illustrates a communications system 900 which uses a commonstate information database 910 that can be accessed by multipleserver's, e.g., authentication, authorization and accounting (AAA)servers 904, 904′. State information can be retrieved and stored in thedatabase 910 by individual servers 904, 904′ in accordance with thepresent invention, e.g., as part of a handoff operation. The operationmay involve a handoff of an end node 946 from a first access node 940 toa second access node 940′.

In the illustrated system 900 end node X 946 has communications links510, 550 with the first and second access nodes 940, 940′, respectively.The system 900 includes one or more additional nodes 120 which performrouting operations. The FIG. 10 system is similar to the systempreviously described in regard to FIG. 5 and can be implemented usingthe same or similar elements, e.g., access node and/or server circuitry.Notably the system in FIG. 10 differs from the FIG. 5 system in terms ofwhere state information is stored in the network and the way in whichservers access and update the state information. In the FIG. 10embodiment, a database 910 which is external to the AAA servers 904,904′ is used to store state information. This allows multiple AAAservers to share a common state information database 910 avoiding theneed to maintain a separate state information database in each AAAserver 904, 904′. This also avoids the need to pass messages between AAAservers 904, 904′ as part of a handoff operation as will now beexplained in the context of an exemplary handoff operation. Furthermore,it increases the reliability of the system in that the failure of anindividual AAA server, e.g.: AAA server 904, does not impact the statetransfer process since any AAA server, e.g.: AAA server 904′, canretrieve state that was put in the database 910 by any other AAA servere.g.: AAA server 904 connected in the same database 910.

AAA protocols use different sets of messages forAuthentication/Authorization (also call AA) e.g.: AccessRequests/Replies and different messages for Accounting (also called A)e.g.: Accounting Requests/Replies. Also the AA part of the AAA servertypically just reads the database to retrieve the user profile. That is,the authentication/authorization part normally does not write in thedatabase. The Accounting part of the AAA server, however, typicallywrites in the database to store the accumulated accounting informationfor a given end node. Typically the records created by the Accountingserver are separate from those created by the AA part of the AAA server.The AA and A parts of the AAA system are logically considered to be onething (i.e.: AAA), yet in some case the AA and A parts of the AAA systemmay be physically separated, e.g., on different servers which comprisepart of the database 910.

In one embodiment of the invention depicted in FIG. 5, messages 520′,530′, 560′ and 570′ are implemented based on new and novel extensions toAuthentication/Authorization messages. In FIG. 10 End Node X 946 sends,e.g., at the start of a handoff, a Store State Request (SSRQ) message510 to Access Node 940 comprising the End Node X 146 identifier. In onesuch implementation of the FIG. 10 embodiment, the end node identifieris the Network Access Identifier (NAI) typically in the format: username@realm. On reception of the SSRQ message 510 the Access Node 940searches its State Management data 313 (FIG. 3) for state informationassociated with said end node and sends an Authentication/AuthorizationAccess_Request message 520′, equivalent to the AN-STU message 520 inFIG. 5, to the AAA Server 904. Said Access_Request message 520′comprises the End Node X 146 identifier (e.g.: NAI) and state associatedwith said end node as available to Access Node 140′. The state istransported in some cases in new and novel extensions to Access_Requestmessages. In one embodiment of this invention said extensions areAttribute-Value-Pairs (AVPs), where an Attribute is the type of state(e.g.: protocol ID) and Value is the actual state information. In analternative embodiment one AVP is used with Attribute an indicatinggeneral state and Value including all state associated with said endnode 946 now carried as an opaque object.

On reception of the Access_Request message 520′ the AAA Server 904processes the message and sends a database_write message 905 to thedatabase to store the state included in said message such that saidstate is associated with the identifier of the end node also included insaid message. The database 910 returns a database_write_ack message 906to the AAA server 904 indicating the success of the write operation. TheAAA node 904 also returns a novel version of Access_Accept message 530′to Access Node 940 indicating the correct reception and storage of saidstate, rather than the typical grant of access to an end node.

End Node X 946 sends a Retrieve State Request (RSRQ) message 550 toAccess Node 940′ comprising the End Node X 146 identifier (e.g.: itsNAI). On reception of said RSRQ message 550 Access Node 940′ sends aAuthentication/Authorization Access_Request message 560′ (equivalent toSTRQ message 560 in FIG. 5) comprising the identifier of End Node X 146(e.g.: its NAI) to the AAA Server 904′. Note that message 560′ is shownto be sent to an AAA server, i.e.: AAA Server 904′ that is differentfrom the server to which the earlier message 520′ was directed. This isshown to illustrate that it is not required all the Access Nodes (e.g.:940, 940′) use the same AAA server (904 or 904′) as long as the AAAservers (904 and 904′) can access the same database 910.

On reception of said Access request message 560′, AAA Server 904′processes said message and sends database_read message 907, comprisingthe end node 946 NAI, to database 910. On reception of message 910 thedatabase searches its memory for state information associated with theEnd Node X 946 indicated in said database_read message. State associatedwith End Node X 946 that was earlier stored is found and a the database910 returns the state in message 908 to the AAA server 904′. Onreception of said message 908, AAA server 904′ sends Access_Acceptmessage 570′ (equivalent to CSMN-STU message 570 in FIG. 5) to AccessNode 940′ including said state and the NAI of End Node X 946.

On reception of Access_Accept message 570′, Access Node 940′ storesstate included in said message in its state management data 313 (FIG. 3)and grants access to end node 946.

In one embodiment of this invention it is possible that on reception ofmessage 907 the database 910 has no dynamic state associated with saidend node 946. In this case database 910 may have static state associatedwith end node 946 in the form of user profile that is not contexttransferred. In this case the static state for end node 946 is returnedto AAA Server 904′ via message 908. In this case AAA server 904′ maystart normal authentication procedures between itself and End Node 946before it returns Access_Accept. This characteristic of the inventionintegrates normal end node authentication with context transfer creatinga consistent and robust method for accepting end nodes into the systemwither for the first time or following a handoff.

The same or similar functionality can be implemented based on theAccounting part of the AAA server by any expert in the art.

In various embodiments nodes described herein are implemented using oneor more modules to perform the steps corresponding to one or moremethods of the present invention, for example, signal processing,message generation and/or transmission steps. Thus, in some embodimentsvarious features of the present invention are implemented using modules.Such modules may be implemented using software, hardware or acombination of software and hardware. Many of the above describedmethods or method steps can be implemented using machine executableinstructions, such as software, included in a machine readable mediumsuch as a memory device, e.g., RAM, floppy disk, etc. to control amachine, e.g., general purpose computer with or without additionalhardware, to implement all or portions of the above described methods,e.g., in one or more nodes. Accordingly, among other things, the presentinvention is directed to a machine-readable medium including machineexecutable instructions for causing a machine, e.g., processor andassociated hardware, to perform one or more of the steps of theabove-described method(s).

Numerous additional variations on the methods and apparatus of thepresent invention described above will be apparent to those skilled inthe art in view of the above description of the invention. Suchvariations are to be considered within the scope of the invention. Themethods and apparatus of the present invention may be, and in variousembodiments are, used with CDMA, orthogonal frequency divisionmultiplexing (OFDM), or various other types of communications techniqueswhich may be used to provide wireless communications links betweenaccess nodes and mobile nodes. In some embodiments the access nodes areimplemented as base stations which establish communications links withmobile nodes using OFDM and/or CDMA. In various embodiments the mobilenodes are implemented as notebook computers, personal data assistants(PDAs), or other portable devices including receiver/transmittercircuits and logic and/or routines, for implementing the methods of thepresent invention.

1. A communications method implemented by a core state management node,the method comprising: receiving from a first access node stateinformation, said state information having been communicated in responseto a signal received by said first access node; storing said stateinformation; receiving a signal from a second access node; andtransmitting said state information to said second access node inresponse to said signal received from said second access node.
 2. Themethod of claim 1, wherein the first and second access nodes are basestations.
 3. The method of claim 1, wherein said signal received fromsaid second access node includes a mobile node identifier.
 4. The methodof claim 3, wherein said signal received by said first access node is asignal from said mobile node.
 5. The method of claim 2, furthercomprising the step of: transmitting, by at least one of the first andsecond access node, a routing update signal to a routing device aftersaid state information is transmitted to said second access node.
 6. Themethod of claim 1, wherein said first access node is in a first networkregion and said second access node is in a second network region, saidstate management node being used to store state information for mobilenodes accessing said system through an access node in said first region.7. The method of claim 5, wherein said state management node is alsoused to store state information for mobile nodes accessing said systemthrough an access node in said second region.
 8. The method of claim 3,further comprising the step of: determining, by the second access node,whether it has received state information corresponding to said mobilenode prior to generating said signal received by said core statemanagement node.
 9. A core state management node for use in acommunications system including a first access node, a second accessnode, said core state management node, and a mobile node, the core statemanagement node comprising: means for receiving from the first accessnode state information, said state information having been communicatedin response to a signal received by said first access node; means forstoring said state information; wherein said means for receiving is alsofor receiving a signal from said second access node; and means fortransmitting said state information to said second access node inresponse to said signal from said second access node.
 10. The core statemanagement node of claim 9, wherein the first and second access nodesare base stations.
 11. The core state management node of claim 9,wherein said signal received from said second access node includes amobile node identifier.
 12. A core state management node for use in acommunications system including a first access node, a second accessnode, said core state management node, and a mobile node, the core statemanagement node comprising: a receiver for receiving from the firstaccess node state information, said state information having beencommunicated in response to a signal received by said first access node;a memory for storing said state information; wherein said receiver isalso for receiving a signal from said second access node; and atransmitter for transmitting said state information to said secondaccess node in response to said signal from said second access node. 13.The core state management node of claim 12, wherein the first and secondaccess nodes are base stations.
 14. The core state management node ofclaim 13, wherein said signal received from said second access nodeincludes a mobile node identifier.
 15. A non-transitory machine readablemedium embodying machine executable instructions for controlling a corestate management node in a communications system including a firstaccess node, a second access node, said core state management node, anda mobile node, the machine readable medium comprising: instructions forcausing the core state management node to receive from the first accessnode state information, said state information having been communicatedin response to a signal received by said first access node; instructionsfor causing the core state management node to store said stateinformation; instructions for causing the core state management node toreceive a signal from said second access node; and instructions forcausing the core state management node to transmit said stateinformation to said second access node in response to said signalreceived from said second access node.
 16. The machine readable mediumof claim 15, wherein the first and second access nodes are basestations.
 17. The machine readable medium of claim 15, wherein saidsignal received from said second access node includes a mobile nodeidentifier.
 18. A core state management node for use in a communicationssystem including a first access node, a second access node, said corestate management node, and a mobile node, the core state management nodecomprising: a processor configured to control said core state managementnode to: receive from the first access node state information, saidstate information having been communicated in response to a signalreceived by said first access node; store said state information;receive a signal from said second access node; and transmit said stateinformation to said second access node in response to said signalreceived from said second access node.
 19. The core state managementnode of claim 18, wherein the first and second access nodes are basestations.
 20. The core state management node of claim 18, wherein saidsignal received from said second access node includes a mobile nodeidentifier.